{Core} Extension Breaking Change Announcement Instruction #30975
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ReaNAiveD
requested review from
jiasli,
evelyn-ys,
jsntcy,
kairu-ms,
zhoxing-ms,
calvinhzy,
necusjz and
bebound
as code owners
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
microsoft-github-policy-service
bot
added
Auto-Assign
ReaNAiveD
requested review from
howang-ms,
Juliehzl,
Greedygre,
yanzhudd,
wangzelin007 and
AllyW
as code owners
ReaNAiveD
force-pushed
the
bc_announce_update
branch
from
6c42404 to
f209cca
Compare
Jacekey23
reviewed
Mar 12, 2025
| * Service Owned Module | ||
| * Service Team should create a Pull Request that create the pre-announcement several sprints ahead Breaking Change Window. | ||
| * The pre-announcement should be released ahead of Breaking Change Window. | ||
| * The pre-announcement should be released at least **2** sprints ahead of Breaking Change Window. |
There was a problem hiding this comment.
usually I suppose sprint will vary across team, but monthly basis is often adopted.
If we put as 1-month policy above(Line 32), we might keep it aligned here, rather than 2 sprints, right?
Jacekey23
reviewed
Mar 12, 2025
| * The pre-announcement should be released ahead of Breaking Change Window. | ||
| * The pre-announcement should be released at least **2** sprints ahead of Breaking Change Window. | ||
| * **Service Owned Module** | ||
| * Service Team should create a Pull Request that adds the pre-announcement at least **2** sprints ahead of Breaking Change Window. |
Jacekey23
reviewed
Mar 12, 2025
| * The pre-announcement should be released at least **2** sprints ahead of Breaking Change Window. | ||
| * **Service Owned Module** | ||
| * Service Team should create a Pull Request that adds the pre-announcement at least **2** sprints ahead of Breaking Change Window. | ||
| * The pre-announcement should be released at least **2** sprints ahead of Breaking Change Window. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related command
Description
Testing Guide
History Notes
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.